Conversation
pedjaradenkovic
left a comment
There was a problem hiding this comment.
From code perspective this looks OK, but I'll ask @dusano to take a look and share his thoughts from product side.
Personally, I'm not a big fan of printing out the attempt numbers as they can seem depressing to the users.
Functionality 3: - :User: should be able to edit :Task: That is, we add functionality number after "Functionality" text. This also saves precious space in TUI.
I think showing just the elapsed time is the right approach. It communicates to the user that something is happening and also educates the user what is the normal duration of each step so that they can take action (ctrl+d) if something takes too long. Therefore I'd like to ask to remove number of attempts from the UI. |
|
Great points. Building on point 3 - would it make sense to add a timer for each state? That is to have timer for the Implementing the functionality, Unit tests, Refactoring and Conformance tests lines? I wanted to iterate quickly on a specific frid and wanted to cancel it early if the Conformance tests state was taking too long - hence I introduced the attempts count and used it as a heuristic for that frid to cancel after eg. 5 attempts. Or if some previous frid was being fixed for more than a few times that I was not expecting it to be fixed I concluded I need to improve the specs of at least one fo those frids. Same would be achievable if there was just a timer for the entire state (not just for the substate of running conformance tests for a specific frid). Maybe also a timer that persists when fixing conformance tests. WDYT? |
|
Thanks for the suggestion but the entire TUI needs to be rethought so I wouldn't focus on it too much other than addressing the most obvious and important issues. |
|
Hey @dusano, just added the changes. Below are the screenshots of the TUI. Here are the changes.
|
|
@zanjonke no further comments from me. This looks good and can be merged and deployed. |




TUI enhancements
This PR introduces TUI enhancements that address some of the feedback that we received during
***plain dev day 2026. It adds more observability to fixing and running unittests and conformance tests.Here are some screenshots (the actual specs and modules names are blurred out). What is new is in red squares.